[Metricbeat] Add region to googlecloud module config#16203
Merged
kaiyan-sheng merged 8 commits intoelastic:masterfrom Feb 21, 2020
kaiyan-sheng:add_region
Merged
[Metricbeat] Add region to googlecloud module config#16203kaiyan-sheng merged 8 commits intoelastic:masterfrom kaiyan-sheng:add_region
kaiyan-sheng merged 8 commits intoelastic:masterfrom
kaiyan-sheng:add_region
Conversation
exekias
reviewed
Feb 11, 2020
Contributor
Author
|
I will revisit this PR after #15598 get merged. |
sayden
approved these changes
Feb 20, 2020
Contributor
sayden
left a comment
There was a problem hiding this comment.
Really good! I'm impressed 😃
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR is to add region as a config parameter in googlecloud module. If region is specified, instances in all zones under that region will be collected.
Why is it important?
This way, if users need to collect metrics from us-west-1a, us-west-1b and us-west-1c, they don't need to specify one section of config for each zone in googlecloud.yml. For example:
Instead, with this PR, only
region: us-west-1is needed in the config:Checklist
How to test this PR locally
Use config below, googlecloud metricset should collect compute metrics from all instances under us-central1 region, which includes us-central1-a, us-central1-b, us-central1-c, and us-central1-f.
Related issues